home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.6 KB | 40 lines | [TEXT/GEOL] |
- Item 0595986 10-July-89 18:12
-
- From: D2215 Dac SW, Wilma Blair, PRT
-
- To: MACAPP.TEST MacApp SQA Team
-
- cc: MACAPP.TECH$ MACAPP Tech
-
- Sub: fShown Schizophrenia
-
- I have found that fShown works differently for windows and views. If a window
- is closed but not freed, fShown is set to false. A subView in that same closed
- window will still have fShown set to true. fShown for a view seems to mean
- "can this view be show" and has nothing to do with whether it is in an open
- window or not. fShown for a Window seems to mean "is this window open (but not
- necessarily visible).
-
- This is ok as I can use fShown to test whether a window is open or closed. I
- can use fIsActive to tell whether it is active and IsShown to tell whether any
- part of it is visible.
-
- This may be a little confusing to a new user of MacApp. Maybe an additional
- field should be added to TWindow called fWindowOpen. fShown would then
- function just like for a view and control whether the window can ever be shown
- (although fShown should be renamed to fCanBeShown to be more clear).
-
- If no new fields can to be added to MacApp 2.0 at this late date, I would at
- least suggest that the IWindow procedure be modified to set fShown to false.
- When a new window is created by procedure, fShown is set true (even though it
- has never been opened). After opening and closing it, it is set to false as it
- should be.
-
- Also, a paragraph might be added to the docs on what the fields really mean and
- how an fShown for a TView means something very diffent than an fShown for a
- TWindow.
-
- Regards, Les Caudle
-
-
-